home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Night Owl 9
/
Night Owl CD-ROM (NOPV9) (Night Owl Publisher) (1993).ISO
/
043a
/
bbsee25a.zip
/
README.2ND
< prev
next >
Wrap
Text File
|
1993-03-28
|
4KB
|
92 lines
Thank you for taking the time to read this file and to evaluate the
shareware program BBSee. I believe that it will become one of your most
used programs. Included with this package is a file QUICKST.ART which
will give you a very quick intro. into BBSee and is MUST reading. To
best understand the program you will also need to read the
documentation, for if you don't you will miss a LOT of power.
The BBSee program and documentation is distributed in two .ZIP files
BBSEE##A.ZIP and BBSEE##B.ZIP. The ## refers to the current version,
which presently is 2.5 (hence BBSEE25A and BBSEE25B). Two other files
BBSEE##X and BBSEE##C (the 'extras' and 'conversion' files) are also
available but they may not be uploaded to every BBS, I leave it up to
users to distribute it. These files are not necessary for BBSee
operation, but they do add power to the use of BBSee. The latest
version of all BBSee files is detailed in BBSee's documentation.
Starting with 2.5 I will distribute BBSEE##U.ZIP which will contain the
primary files required to upgrade to a new version.
=========================================================================
A. WHAT HAS CHANGED IN BBSEE?
The BBSEE25A.ZIP contains the latest version of BBSEE.EXE, with many
program changes since 2.0.
The changes in the BBSEE25B (since 20B) file are minor. The
documentation has of course been changed to cover new features (as
covered in WHATS.NEW). IMPORT.EXE (and BBSee) have been updated to
handle a few more BBS types automatically.
BBSEE25X.ZIP incorporates the following changes:
1) BBC2PCB.EXE was refined in V2.2 to allow output without the PCBoard
'|' character, and with a maximum column width of 78.
2) PACBBSee has been modified to block the archive database in a
slightly more efficient .manner, and also to provide the capability
of rebuilding a corrupt database index file.
BBSEE25C.ZIP incorporates the following changes:
1) The converstion utility from other programs has been completely
rewritten as CATCON.EXE since 2.0. This one program now converts
from CatDisk, Intelicat, Wssindex, DiskTrak, and CUDM. Support for
CatDisk 43 character descriptions was added in 2.3.
2) A new small utility to convert the ASP catalog to a format which can
be imported into BBSee, was added in 2.1
3) Two conversion programs FIX4DIZ.EXE and FIXARC.EXE have been added,
see the following two sections.
=========================================================================
B. FILE_ID.DIZ/DESC.SDI extraction prior to version 2.21
Since BBSee V2.0 came out it has come to my attention that BBSee did not
make the proper allowance to handle these files, if they were created
with an incorrect format. Specifically, these files should NEVER be
more than 512 characters long, but some people did not heed this
specification. BBSee now truncates descriptions with more than 512
characters, but there is a rare case that if you extracted an invalid
description, that existing descriptions in your database were not be
properly handled, which could lead to a hung machine if record buffers
overflowed (especially in Catalog description print reports).
To correct this there is a fixup program FIX4DIZ.EXE contained in the
file BBSEE25C.ZIP.
=========================================================================
C. Error with sub-directory names within archives prior to 2.41
Bugs in BBSee prior to version 2.41 could cause errors in the catalog
filenames with archives for ARJ and ZIP files which had sub-directory
names attached. A conversion utility, contained in BBSEE25C.ZIP,
FIXARC.EXE will remove 'bad' entries from the archive database. If you
feel that your archive database is not correct (from looking the archive
report), run this conversion. This program is relatively slow, in that
it must:
1) completely rebuild the ARCHIVES.IDX file.
2) eliminate any 'bad' archive files (multiple passes may be required).
3) perform a 'pack' on the archive database.
Note that disks with sub-directory information will need to be
recataloged. You may wish to redirect output from FIXARC to get a list
of problem volumes.
Martin Vallevand